home *** CD-ROM | disk | FTP | other *** search
-
- Door Structures
- ---------------
- For the release of Wildcat! 4 we have redone the files that Wildcat
- creates when it running an external program, the only file that remains
- the same is DOOR.SYS which provides compatablility some older style
- doors as well as doors used by RBBS/GAP & PCBOARD.
-
- DOOR.SYS is meant as a universal standard for sharing door programs,
- because of this it does not contain all the information that is required
- for a full blown Wildcat! 4 application. We only create the file, we do
- not check it for changes when the door returns, instead we have three
- other drop files that we use to handle this type of information, they
- are as follows:
-
- SYSINFO.DAT
- -----------
-
- This file contains all the current Wildcat! 4 system information, on
- return from the door Wildcat checks this file and makes the appropriate
- changes to the current running system. This is a standard text file.
-
- Here is the layout for SYSINFO.DAT:
-
- MSI HQ BBS {Line 1 - The current BBS Name }
- 19200 {Line 2 - Current Baud Rate (300-15200 and Local) }
- 8 {Line 3 - Databits }
- Y {Line 4 - 'N' = No color, 'Y' = Ansi, 'R' = Rip }
- Y {Line 5 - MNP connection }
- 52 {Line 6 - Time remaining online }
- 30 {Line 7 - Banked time }
- 14:22 02/22/94 {Line 8 - Time and date of call }
- 14:28 02/22/94 {Line 9 - Time and date entered door }
- N {Line 10 - Started with command line option }
- 20 {Line 11 - Current conference number }
- 1 {Line 12 - Active menu number }
- 3 {Line 13 - Current door number }
- N {Line 14 - Did the caller hang-up in door }
- N {Line 15 - Reserved for future use }
- Y P Z D G {Line 16 - Current commands on command stack }
- SERIAL {Line 17 - Interface type (SERIAL, DIGI, FOSSIL, LOCAL }
- ENGLISH {Line 18 - Current language }
-
- A few notes about line 15, when Wildcat creates the SYSINFO.DAT file it
- takes the contents of the current command stack and writes them to line
- 15, all of the doors that MSI writes takes advantage of this and will
- continue to process the commands, when the door is finished it will write
- the remainder of the stack to line 15 where Wildcat will re-parse the line
- and continue to process it. This provides a seamless interface for callers
- when they are running external programs, Wildcat will accept spaces, commas
- and semi-colons as delimeters.
-
-
- USERREC.BIN
- ------------
-
- This file is a list of all the currently marked files at the time the door
- was started, after Wildcat has created this list it clears the current
- users list in memory and upon returning from the door reads the list back
- into the marked list. This allows doors the ability to add and delete files
- to the current mark list, you are allowed a maximum of 99 files.
- The list contains two types of files, Standard which are files found in the
- current file database and Direct which are files that can be located on
- any logical device.
-
- Here is the layout for FILEINFO.DAT:
-
- 10 {Line 1 - The amount of marked files in this list }
- 2 {1 File 1 - The file area this file came from }
- DRWY221.ZIP {2 File 1 - The actual file name of this file }
- STANDARD {3 File 1 - The type of this file (STANDARD, DIRECT) }
- N {4 File 1 - Is this file on CD ROM }
- N {5 File 1 - Scanned (used by the Thumbnailer) }
- 10 {6 File 1 - Used by the ThumbNailer }
- C:\XFS\DRWY221.ZIP {7 File 1 - Path and filenane of current file }
- 0 {1 File 2 - The file area this file came from }
- TESTFILE.ZIP {2 File 2 - The actual file name of this file }
- DIRECT {3 File 2 - The type of this file (STANDARD, DIRECT) }
- N {4 File 2 - Is this file on CD ROM }
- N {5 File 2 - Scanned (used by the Thumbnailer) }
- 0 {6 File 2 - Used by the ThumbNailer }
- C:\XFS\TESTFILE.ZIP {7 File 2 - Path and filenane of current file }
-
- When you specify a direct file type, the only options that have any meaning
- are Line 2, Line 3 and Line 7. Wildcat will use these lines to present and
- send the file to the user.
-
-
- USERREC.DAT
- -----------
-
- This file is an actual copy of the user's records that Wildcat keeps in
- memory while the user is on the BBS, this is not a text file, it is written
- out as straight binary and must be loaded into a TUserRec structure in order
- to be used by your program. This means you can change any of the users
- information in their current record without ever touching the databases, when
- Wildcat returns from a door it checks to make sure that the USERREC.DAT is
- the correct size before it will load it, if it has been corrupted Wildcat
- will make a note of it in the error.log and continue using the record in
- memory. Make sure you know what you are doing BEFORE you start playing with
- this file, you can cause a user all types of trouble if you accidently set
- some of the fields incorrectly and Wildcat reads the file back in.
-
-
- PROFILE.DAT
- -----------
-
- This file is created at the time the user logs onto the system and anytime
- you upgrade a users access, it contains the users current security profile
- (TSECREC) and all of their seconday profile accesses combined into one file.
- The file is used for checking access to Doors, Menu Items, Protocols, Nodes,
- Conferences and File areas, the file is used by Wildcat and wcMAIL and cannot
- be modified, if you change the file in any way, there is no guarantee as to
- how Wildcat will react.
-
- Here is the format of the file:
-
-
- +----------------------------+
- | |
- | Users Current TSecRec File |
- | |
- +----------------------------+
- | |
- | Conference access bits |
- | |
- | 3 For each conference |
- | |
- +----------------------------+
- | |
- | File access bits |
- | |
- | 3 For each file area |
- | |
- +----------------------------+
-
-
- This layout is identical to the one used in the SECLEVEL.DAT file, except this
- is one single record, for more information on how to read the bits and their
- exact meaning, see the documentation on the SECLEVEL.DAT file.
-
-
-
- DOOR.SYS
- --------
-
-
- 03/14/88 - Submitted by the "Limited Release Software Group"
-
- Updated: 03/21/88
- Updated: 10/22/88 KG
- Updated: 07/07/90 KG, to add additional info for Raymond Clements
- Updated: 07/14/91 Note to developers added by Jim Harrer/Mustang Software.
-
- =============================================================================
-
- Sample DOOR.SYS file to be used as a STANDARD for ALL Bulletin Board Systems.
-
- =============================================================================
-
- This file format has been laid out and will be presented to ALL BBS authors
- in an attempt to establish a national standard for door program applications.
-
- BBS AUTHORS: I urge you to consider this STANDARD with respect for your 3rd
- party support authors. Come on guys, make life EASY for us.
- (BIG GRIN)
-
- =============================================================================
-
- I have tried to include EVERYTHING a 3rd party DOOR author would need to
- provide the SYSOPS with the look and feel they want from an online program
- while at the same time keeping things plain and simple to ease the problems
- of interfacing programs with a system.
-
- This type of format is intended to be a "read-only" type of file
- (although it could be written again) because most BBS's have some sort
- of other file they use for re-entering the system with (PCBoard uses
- PCBOARD.SYS) which is harder to read in, and changes frequently.
- This file format, once established, wouldn't need to be changed EVERYTIME
- a new version of the BBS software gets released and this would also
- ease the demand for more info being made available in the BBS Re-Entry
- file thus making life easier for both parties. If there is something
- found in the following format that your BBS software may not be currently
- supporting, a DEFAULT value has been suggested.
-
- ----------
- KG, Note:
-
- GAP DOES treat this file as Read/Write since GAP does not use
- or have any use for a Door File. GAP will re-read the DOOR.SYS upon
- return from a door. But not all fields are re-read. Only those fields
- that are marked with an '*' will be read by GAP when a caller returns
- from a door.
-
- When reading this file, you should not go into an EOF loop. In
- other words, you should not read until you encounter End Of File.
- Instead, you should read what you KNOW is there. This allows for
- additions to the end of the file without forcing all programs to be
- re-compiled.
-
- ----------
- Note from Jim Harrer:
-
- Beginning with WILDCAT! release 3, we will begin supporting this DOOR.SYS
- Standard by creating this file in the \WC30\WCWORK\NODEx (x = Node Number)
- directory. We will NOT read this file back in. If DOORS wish to change
- any of the callers variables, then the door author should refer to our
- USERINFO.DAT standard.
-
- Mustang Software will not support any future changes to DOOR.SYS. Other
- BBS authors must regard this DOOR.SYS as a "Standard" and not change or
- add to it in any way. DOOR authors can be assured we will not change
- DOOR.SYS in the future. Any changes we need to make will be done to our
- USERINFO.DAT standard.
-
- I hope other BBS authors will join us in agreement of not making any
- additional changes to DOOR.SYS in the future.
-
- ----------
- DOOR.SYS
- --------
- COM1: <-- Comm Port - COM0: = LOCAL MODE
- 2400 <-- Baud Rate - 300 to 38400
- 8 <-- Parity - 7 or 8
- 1 <-- Node Number - 1 to 99 (Default to 1)
- 19200 <-- DTE Rate. Actual BPS rate to use. (kg)
- Y <-- Screen Display - Y=On N=Off (Default to Y)
- Y <-- Printer Toggle - Y=On N=Off (Default to Y)
- Y <-- Page Bell - Y=On N=Off (Default to Y)
- Y <-- Caller Alarm - Y=On N=Off (Default to Y)
- Rick Greer <-- User Full Name
- Lewisville, Tx. <-- Calling From
- 214 221-7814 <-- Home Phone
- 214 221-7814 <-- Work/Data Phone
- PASSWORD <-- Password
- 110 *<-- Security Level
- 1456 <-- Total Times On
- 03/14/88 <-- Last Date Called
- 7560 <-- Seconds Remaining THIS call (for those that particular)
- 126 <-- Minutes Remaining THIS call
- GR <-- Graphics Mode - GR=Graph, NG=Non-Graph, 7E=7,E Caller
- 23 <-- Page Length
- Y <-- User Mode - Y = Expert, N = Novice
- 1,2,3,4,5,6,7 <-- Conferences/Forums Registered In (ABCDEFG)
- 7 <-- Conference Exited To DOOR From (G)
- 01/01/99 <-- User Expiration Date (mm/dd/yy)
- 1 <-- User File's Record Number
- Y <-- Default Protocol - X, C, Y, G, I, N, Etc.
- 0 *<-- Total Uploads
- 0 *<-- Total Downloads
- 0 *<-- Daily Download "K" Total
- 999999 <-- Daily Download Max. "K" Limit
- 10/22/88 <-- Caller's Birthdate (kg)
- G:\GAP\MAIN <-- Path to the MAIN directory (where User File is) (kg)
- G:\GAP\GEN <-- Path to the GEN directory (kg)
- Michael <-- Sysop's Name (name BBS refers to Sysop as) (kg)
- Stud <-- Alias name (rc)
- 00:05 <-- Event time (hh:mm) (rc)
- Y <-- If its an error correcting connection (Y/N) (rc)
- N <-- ANSI supported & caller using NG mode (Y/N) (rc)
- Y <-- Use Record Locking (Y/N) (rc)
- 14 <-- BBS Default Color (Standard IBM color code, ie, 1-15) (rc)
- 10 *<-- Time Credits In Minutes (positive/negative) (rc)
- 07/07/90 <-- Last New Files Scan Date (mm/dd/yy) (rc)
- 14:32 <-- Time of This Call (hh:mm) (rc)
- 07:30 <-- Time of Last Call (hh:mm) (rc)
- 6 <-- Maximum daily files available (rc)
- 3 *<-- Files d/led so far today (rc)
- 23456 *<-- Total "K" Bytes Uploaded (rc)
- 76329 *<-- Total "K" Bytes Downloaded (rc)
- A File Sucker <-- User Comment (rc)
- 10 <-- Total Doors Opened (rc)
- 10283 <-- Total Messages Left (rc)
-
-
- ***** Each line is STRAIGHT ASCII TEXT with a CR/LF at the end. *****
-
- Lines marked with an '*' will be re-read in GAP when a caller
- returns from a door.
-
- Rick Greer, the author of this Universal Specification, is no
- where to be found!
-
-
-
-